Transport sound profile

ABSTRACT

An example operation includes one or more of associating a vehicle with an impact, saving media captured before and after the impact as a media segment, transmitting, by a computing device associated with the vehicle, the media segment to another computing device, and building a sound profile from the media segment.

TECHNICAL FIELD

This application generally relates to building a sound profile from amedia segment related to a vehicle impact, and more particularly, to atransport sound profile.

BACKGROUND

Transports, such as cars, motorcycles, trucks, planes, trains, etc.,generally provide transportation needs to occupants and/or goods in avariety of ways. Functions related to transports may be identified andutilized by various computing devices, such as a smartphone or acomputer.

Evidence and data for vehicular accidents takes much time to gather andprocess. In many cases, trained accident forensics investigators must bephysically at the accident scene and personally gather evidence overhours. What is needed is a process to combine existing media capturedevices and technologies in transports and with almost all pedestrians.Video and audio, along with other forms of data, are provided to acomputing device that processes the media and creates immediately usablecontent for requiring organizations, The present application disclosesobtaining media both preceding and immediately following a vehicularaccident. The media is transferred to a computing device, and a soundprofile is constructed from the media. The sound profile includesanalysis that may be useful to first responders, law enforcement, orinsurance providers.

SUMMARY

One example embodiment provides a method that includes one or more ofassociating a vehicle with an impact, saving media captured before andafter the impact as a media segment, and transmitting, by a computingdevice associated with the vehicle, the media segment to anothercomputing device, and building a sound profile from the media segment.

Another example embodiment provides a vehicle that includes a processorand a memory, coupled to the processor. The memory includes instructionsthat when executed by the processor are configured to perform one ormore of detect an impact, save media captured before and after theimpact as a media segment, transmit, by a computing device associatedwith the vehicle, the media segment to another computing device andbuild a sound profile from the media segment.

A further example embodiment provides a non-transitory computer readablemedium comprising instructions, that when read by a processor, cause theprocessor to perform one or more of associating a vehicle with animpact, saving media captured before and after the impact as a mediasegment, transmitting, by a computing device associated with thevehicle, the media segment to another computing device, and building asound profile from the media segment.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a diagram illustrating obtaining sounds from a transport inan impact, according to example embodiments.

FIG. 1B is a diagram illustrating obtaining multimedia content fromdevices within geolocation boundaries, according to example embodiments.

FIG. 1C is a diagram illustrating capturing media from transports withina geofence following a dangerous driving situation, according to exampleembodiments.

FIG. 1D is a diagram illustrating building a sound profile from a mediasegment corresponding to a transport impact, according to exampleembodiments.

FIG. 2A illustrates a transport network diagram, according to exampleembodiments.

FIG. 2B illustrates another transport network diagram, according toexample embodiments.

FIG. 2C illustrates yet another transport network diagram, according toexample embodiments.

FIG. 2D illustrates a further transport network diagram, according toexample embodiments.

FIG. 2E illustrates a yet further transport network diagram, accordingto example embodiments.

FIG. 2F illustrates a yet further transport network diagram, accordingto example embodiments.

FIG. 3A illustrates a flow diagram, according to example embodiments.

FIG. 3B illustrates another flow diagram, according to exampleembodiments.

FIG. 3C illustrates yet another flow diagram, according to exampleembodiments.

FIG. 3D illustrates yet another flow diagram, according to exampleembodiments.

FIG. 4 illustrates a machine learning transport network diagram,according to example embodiments.

FIG. 5A illustrates an example transport configuration for managingdatabase transactions associated with a transport, according to exampleembodiments.

FIG. 5B illustrates another example transport configuration for managingdatabase transactions conducted among various transports, according toexample embodiments.

FIG. 6A illustrates a blockchain architecture configuration, accordingto example embodiments.

FIG. 6B illustrates another blockchain configuration, according toexample embodiments.

FIG. 6C illustrates a blockchain configuration for storing blockchaintransaction data, according to example embodiments.

FIG. 6D illustrates example data blocks, according to exampleembodiments.

FIG. 7 illustrates an example system that supports one or more of theexample embodiments.

DETAILED DESCRIPTION

It will be readily understood that the instant components, as generallydescribed and illustrated in the figures herein, may be arranged anddesigned in a wide variety of different configurations. Thus, thefollowing detailed description of the embodiments of at least one of amethod, apparatus, non-transitory computer readable medium and system,as represented in the attached figures, is not intended to limit thescope of the application as claimed but is merely representative ofselected embodiments.

The instant features, structures, or characteristics as describedthroughout this specification may be combined in any suitable manner inone or more embodiments. For example, the usage of the phrases “exampleembodiments”, “some embodiments”, or other similar language, throughoutleast this specification refers to the fact that a particular feature,structure, or characteristic described in connection with the embodimentmay be included in at one embodiment. Thus, appearances of the phrases“example embodiments”, “in some embodiments”, “in other embodiments”, orother similar language, throughout this specification do not necessarilyall refer to the same group of embodiments, and the described features,structures, or characteristics may be combined in any suitable manner inone or more embodiments. In the diagrams, any connection betweenelements can permit one-way and/or two-way communication even if thedepicted connection is a one-way or two-way arrow. In the currentapplication, a transport may include one or more of vehicles, cars,trucks, motorcycles, scooters, bicycles, boats, recreational transports,planes, and any object that may be used to transport people and or goodsfrom one location to another.

In addition, while the term “message” may have been used in thedescription of embodiments, the application may be applied to many typesof network data, such as, a packet, frame, datagram, etc. The term“message” also includes packet, frame, datagram, and any equivalentsthereof. Furthermore, while certain types of messages and signaling maybe depicted in exemplary embodiments they are not limited to a certaintype of message, and the application is not limited to a certain type ofsignaling.

Example embodiments provide methods, systems, components, non-transitorycomputer readable media, devices, and/or networks, which provide atleast one of: a transport (also referred to as a transport herein) adata collection system, a data monitoring system, a verification system,an authorization system and a transport data distribution system. Thetransport status condition data, received in the form of communicationupdate messages, such as wireless data network communications and/orwired communication messages, may be received and processed to identifytransport/transport status conditions and provide feedback as to thecondition changes of a transport. In one example, a user profile may beapplied to a particular transport/transport to authorize a currenttransport event, service stops at service stations, and to authorizesubsequent transport rental services.

Within the communication infrastructure, a decentralized database is adistributed storage system which includes multiple nodes thatcommunicate with each other. A blockchain is an example of adecentralized database which includes an append-only immutable datastructure (i.e. a distributed ledger) capable of maintaining recordsbetween untrusted parties. The untrusted parties are referred to hereinas peers, nodes or peer nodes. Each peer maintains a copy of thedatabase records and no single peer can modify the database recordswithout a consensus being reached among the distributed peers. Forexample, the peers may execute a consensus protocol to validateblockchain storage entries, group the storage entries into blocks, andbuild a hash chain via the blocks. This process forms the ledger byordering the storage entries, as is necessary, for consistency. In apublic or permissionless blockchain, anyone can participate without aspecific identity. Public blockchains can involve cryptocurrencies anduse consensus based on various protocols such as proof of work (PoW). Onthe other hand, a permissioned blockchain database provides a systemwhich can secure interactions among a group of entities which share acommon goal, but which do not or cannot fully trust one another, such asbusinesses that exchange funds, goods, information, and the like. Theinstant application can function in a permissioned and/or apermissionless blockchain setting.

Smart contracts are trusted distributed applications which leveragetamper-proof properties of the shared or distributed ledger (i.e., whichmay be in the form of a blockchain) database and an underlying agreementbetween member nodes which is referred to as an endorsement orendorsement policy. In general, blockchain entries are “endorsed” beforebeing committed to the blockchain while entries which are not endorsedare disregarded. A typical endorsement policy allows smart contractexecutable code to specify endorsers for an entry in the form of a setof peer nodes that are necessary for endorsement. When a client sendsthe entry to the peers specified in the endorsement policy, the entry isexecuted to validate the entry. After validation, the entries enter anordering phase in which a consensus protocol is used to produce anordered sequence of endorsed entries grouped into blocks.

Nodes are the communication entities of the blockchain system. A “node”may perform a logical function in the sense that multiple nodes ofdifferent types can run on the same physical server. Nodes are groupedin trust domains and are associated with logical entities that controlthem in various ways. Nodes may include different types, such as aclient or submitting-client node which submits an entry-invocation to anendorser (e.g., peer), and broadcasts entry-proposals to an orderingservice (e.g., ordering node). Another type of node is a peer node whichcan receive client submitted entries, commit the entries and maintain astate and a copy of the ledger of blockchain entries. Peers can alsohave the role of an endorser, although it is not a requirement. Anordering-service-node or orderer is a node running the communicationservice for all nodes, and which implements a delivery guarantee, suchas a broadcast to each of the peer nodes in the system when committingentries and modifying a world state of the blockchain, which is anothername for the initial blockchain entry which normally includes controland setup information.

A ledger is a sequenced, tamper-resistant record of all statetransitions of a blockchain. State transitions may result from smartcontract executable code invocations (i.e., entries) submitted byparticipating parties (e.g., client nodes, ordering nodes, endorsernodes, peer nodes, etc.). An entry may result in a set of assetkey-value pairs being committed to the ledger as one or more operands,such as creates, updates, deletes, and the like. The ledger includes ablockchain (also referred to as a chain) which is used to store animmutable, sequenced record in blocks. The ledger also includes a statedatabase which maintains a current state of the blockchain. There istypically one ledger per channel. Each peer node maintains a copy of theledger for each channel of which they are a member.

A chain is an entry log which is structured as hash-linked blocks, andeach block contains a sequence of N entries where N is equal to orgreater than one. The block header includes a hash of the block'sentries, as well as a hash of the prior block's header. In this way, allentries on the ledger may be sequenced and cryptographically linkedtogether. Accordingly, it is not possible to tamper with the ledger datawithout breaking the hash links. A hash of a most recently addedblockchain block represents every entry on the chain that has comebefore it, making it possible to ensure that all peer nodes are in aconsistent and trusted state. The chain may be stored on a peer nodefile system (i.e., local, attached storage, cloud, etc.), efficientlysupporting the append-only nature of the blockchain workload.

The current state of the immutable ledger represents the latest valuesfor all keys that are included in the chain entry log. Because thecurrent state represents the latest key values known to a channel, it issometimes referred to as a world state. Smart contract executable codeinvocations execute entries against the current state data of theledger. To make these smart contract executable code interactionsefficient, the latest values of the keys may be stored in a statedatabase. The state database may be simply an indexed view into thechain's entry log, it can therefore be regenerated from the chain at anytime. The state database may automatically be recovered (or generated ifneeded) upon peer node startup, and before entries are accepted.

A blockchain is different from a traditional database in that theblockchain is not a central storage but rather a decentralized,immutable, and secure storage, where nodes must share in changes torecords in the storage. Some properties that are inherent in blockchainand which help implement the blockchain include, but are not limited to,an immutable ledger, smart contracts, security, privacy,decentralization, consensus, endorsement, accessibility, and the like.

Example embodiments provide a way for providing a transport service to aparticular transport and/or requesting user associated with a userprofile that is applied to the transport. For example, a user may be theowner of a transport or the operator of a transport owned by anotherparty. The transport may require service at certain intervals and theservice needs may require authorization prior to permitting the servicesto be received. Also, service centers may offer services to transportsin a nearby area based on the transport's current route plan and arelative level of service requirements (e.g., immediate, severe,intermediate, minor, etc.). The transport needs may be monitored via oneor more sensors which report sensed data to a central controllercomputer device in the transport, which in turn, is forwarded to amanagement server for review and action.

A sensor may be located on one or more of the interior of the transport,the exterior of the transport, on a fixed object apart from thetransport, and on another transport near to the transport. The sensormay also be associated with the transport's speed, the transport'sbraking, the transport's acceleration, fuel levels, service needs, thegear-shifting of the transport, the transport's steering, and the like.The notion of a sensor may also be a device, such as a mobile device.Also, sensor information may be used to identify whether the transportis operating safely and whether the occupant user has engaged in anyunexpected transport conditions, such as during the transport accessperiod. Transport information collected before, during and/or after atransport's operation may be identified and stored in a transaction on ashared/distributed ledger, which may be generated and committed to theimmutable ledger as determined by a permission granting consortium, andthus in a “decentralized” manner, such as via a blockchain membershipgroup.

Each interested party (i.e., company, agency, etc.) may want to limitthe exposure of private information, and therefore the blockchain andits immutability can limit the exposure and manage permissions for eachparticular user transport profile. A smart contract may be used toprovide compensation, quantify a user profile score/rating/review, applytransport event permissions, determine when service is needed, identifya collision and/or degradation event, identify a safety concern event,identify parties to the event and provide distribution to registeredentities seeking access to such transport event data. Also, the resultsmay be identified, and the necessary information can be shared among theregistered companies and/or individuals based on a “consensus” approachassociated with the blockchain. Such an approach could not beimplemented on a traditional centralized database.

Every autonomous driving system is built on a whole suite of softwareand an array of sensors. Machine learning, lidar projectors, radar, andultrasonic sensors all work together to create a living map of the worldthat a self-driving car can navigate. Most companies in the race to fullautonomy are relying on the same basic technological foundations oflidar+radar+cameras+ultrasonic, with a few notable exceptions.

In another embodiment, GPS, maps and other cameras and sensors are usedin autonomous transports without lidar as lidar is often viewed as beingexpensive and unnecessary. Researchers have determined that stereocameras are a low-cost alternative to the more expensive lidarfunctionality.

The instant application includes, in certain embodiments, authorizing atransport for service via an automated and quick authentication scheme.For example, driving up to a charging station or fuel pump may beperformed by a transport operator and the authorization to receivecharge or fuel may be performed without any delays provided theauthorization is received by the service station. A transport mayprovide a communication signal that provides an identification of atransport that has a currently active profile linked to an account thatis authorized to accept a service which can be later rectified bycompensation. Additional measures may be used to provide furtherauthentication, such as another identifier may be sent from the user'sdevice wirelessly to the service center to replace or supplement thefirst authorization effort between the transport and the service centerwith an additional authorization effort.

Data shared and received may be stored in a database, which maintainsdata in one single database (e.g., database server) and generally at oneparticular location. This location is often a central computer, forexample, a desktop central processing unit (CPU), a server CPU, or amainframe computer. Information stored on a centralized database istypically accessible from multiple different points. A centralizeddatabase is easy to manage, maintain, and control, especially forpurposes of security because of its single location. Within acentralized database, data redundancy is minimized as a single storingplace of all data also implies that a given set of data only has oneprimary record.

FIG. 1A is a diagram illustrating obtaining sounds from a transport inan impact 100, according to example embodiments. Transports or 104 maysometimes be involved in an impact incident. Impacts may be with astationary object as shown, such as a light pole, a building, or variouspermanent or temporary structures. Impacts may also be with one or moreother transports 108. In some cases, instead of a direct impact orcollision with a stationary object or another transport 104, theembodiments associated with FIG. 1A may also be associated with anear-impact or a dangerous driving situation. Examples of a near-impactor a dangerous driving situation may include hard breaking, swerving,weaving in traffic, driving into and/or across lanes, driving off road,tailgating, not stopping at stop signs, running red lights, or any othersimilar type of event.

Later model transports 104 include various computers, communicationdevices, and sensors. These resources collectively provide navigationfunctions, hands-free communication, parking assistance, collisiondetection, and monitoring of nearby other transports 108 in order toprovide more information and convenience to passengers and reduce theopportunity for impacts or accidents. These computers, communicationdevices, and sensors may communicate with other computers, communicationdevices, and sensors either within or outside of the transport 104through various technologies such as a transport's Controller AreaNetwork (CAN) bus, BLUETOOTH, WIFI, or the like.

Transports 104 and other transports 108 may include any type ofself-propelled conveyance, including cars, motorcycles, trucks,construction equipment, or even local single passenger transports 104,108 such as SEGWAYs or similar devices. Transports 104, 108 may have ahuman driver or be a driverless transport, and may or may not have anypassengers. Transports 104, 108 may include cargo transports includingdelivery vans, mail delivery transports, and unmanned package deliverydrones.

Transports 104 may include one or more front, rear, side, ordash-mounted devices such as cameras to capture and display video to thedriver, and possibly to transmit outside the transport 104. Transports104 may also include microphones to capture audio both inside the cabinas well as outside as well. Such audio may be used to communicate withoutside driver assistance services such as ONSTAR or similar. In somecases, the audio may accompany video from one or more onboard cameras.

Transports 104 often include hand-free wireless interfaces in order tomore safely utilize mobile communication devices such as cell phones,smart phones, or various tablets and other communication devices. Theseinterfaces may operate with embedded applications such as CARPLAY toreplicate mobile device applications and functionality with transport104 entertainment, communication, or computing devices.

With transports 104 now able to communicate more globally with outsideservices and communication providers, it may be beneficial to identifyindividual transports 104 in order to distinguish from other transports108. Thus, an identifier may be permanently stored or assigned to eachtransport 104, and the identifier may accompany any rich media content112 (i.e. any combination of static images, video, audio, sensor data,etc) transmitted from the transport 104. Sensor data may include radardata, sonar data, magnetic detector data, optical sensor data, laserrangefinder data, or any other form of data produced by sensorsassociated with the transport 104, 108.

When a transport 104 is involved with an impact or accident, aspreviously discussed, the transport 104 is associated with the impact.In one embodiment, an event is created within an onboard computer oftransport 104, and the transport 104 identifier is associated with theevent. In one embodiment, the onboard computer may include a memorydevice to store the event and associated identifier. In one embodiment,the impact or accident is in proximity to one or more other transports108. Proximity may be determined by several means, including a distancefrom a location, a distance from a GPS coordinate, a streetintersection, a line of sight, a hearing limit, a same street, or astreet address range. In one embodiment, the proximity may be associatedwith a distance from the impact defined by a geofence. Within proximityof the impact, there may be any number of other transports 108 and anynumber of devices 120, such as devices associated with an individual.Devices 120 may include any type of communication devices, includingcell phones, smart phones, tablets, smart watches, wearable computers,or implantable computers. Devices 120 may be in the possession of apedestrian, bicycle rider, transport 104, 108 driver, or transport 104,108 passenger. Device 120 may also be a static device within proximityof the impact, including traffic cameras, business video cameras, oraerial drone-mounted cameras. Devices 120 may also include inherent(i.e. part of the transport 104, 108) communication devices notassociated with or in the possession of any individual.

When an impact or accident occurs, a device 120 in proximity to theimpact transmits media and/or data 112 related to the impact to a server116. The media 112 may include any combination of an audio file, a videofile, a text file, an image file, transport telemetry, environmentaldata, traffic data, or sensor data. In one embodiment, the media 112 mayalso include a direction for each of the sounds.

In one embodiment, a transport 104 associated with the impact maytransmit the media 112. In another embodiment, another transport 108 notassociated with the impact may transmit the media 112. In anotherembodiment, a device 120 associated with a bystander or pedestrian inproximity to the impact may transmit the media 112. In yet anotherembodiment, a device 120 associated with a passenger of the transport104 associated with the impact or a device 120 associated with apassenger of another transport 108 not associated with the impact maytransmit the media 112. In yet another embodiment, a device 120associated with static camera or sensor in proximity to the impact oraccident may transmit the media 112.

The server 116 may be located anywhere, including in proximity to theimpact or accident or outside the proximity to the impact or accident.The server 116 receives the media 112 over any type of data connection,but most likely through wireless connections, including but not limitedto cellular connections (i.e. 3G, 4G, 5G, LTE), internet or broadbandconnections, WIFI connections, or the like. The server 116 may includeone or more applications in a memory 706, which may determine or moresounds based on the media 112. Each of the sounds may include anidentification of a type of sound source (e.g. an automotive noise of atransport 104, an automotive noise of another transport 108, an impactsound associated with the transport 104, a human voice or exclamation, awarning alarm, a skidding transport 104, 108, or any other type ofdetected sound), a time stamp associated with a sound, a sound level orvolume of the sound, a sound duration of time, and an indication ofassociation with a different sound (e.g. a passenger voice of apassenger within the transport 104). In one embodiment, determining oneor more sounds based on the media 112 may include time stamping one ormore of a start time and an end time for each sound and identifying asound source for each of the one or more sounds. The sounds may havebeen recorded by the device 120 within a first predetermined time beforethe impact or accident and a second predetermined time after the impactor accident.

Determining the one or more sounds based on the media 112 may in someembodiments result in a file created by the server 116 with a group ofparameters (identifiers, time stamps, etc as previously discussed). Insome embodiments, the file may be transmitted by the server 116 orstored in a database (not shown). The server 116 may include one or moreapplications that perform speech recognition on sounds identified asvoices. In one embodiment, the speech recognition application maydetermine a context based on recognized speech, where the context mayinclude a location, a threat, a cause of the impact or accident, a fireor explosion, an injury or medical status, a name, an action, acontrolled substance, a hazardous material, a crime, or actual orimplied violence. In one embodiment, law enforcement may be notified ifthe context is applicable to law enforcement. In one embodiment, EMS ora fire department may be notified if the context is applicable to amedical condition, a fire, a hazardous material, or an explosion. In oneembodiment, an insurance provider may be notified if the context isapplicable to a cause of the impact or accident. The media 112 mayinclude any number of videos. In one embodiment, the server 116determines a number of videos based on the received media 112 andsynchronizes sounds with the videos. This helps to establish morecontext for improved understanding by combining different but relatedmedia types 112.

Once the server 116 has determined one or more sounds based on the media112, the server 116 may associate sounds (from devices 120 in proximityto the impact or accident) with the transport 104 involved in the impactor accident or another transport 108. By performing this association,the server 116 creates a data-driven narrative of the impact event thathelps describe the roles and contribution to the impact by thetransports 104, 108. It should be noted that any of the actions takenwith respect to an impact or accident herein apply equally to bothnear-impacts as well as dangerous driving situations.

FIG. 1B is a diagram illustrating obtaining multimedia content fromdevices within geolocation boundaries 130, according to exampleembodiments. Transports 104 may sometimes be involved in an impactincident or collision. It is advantageous to gather relevant dataquickly after an impact or accident. Relevant data is generally local tothe impact or accident, where “local” may be defined in different ways.Data that is not local to the impact or accident may be considered asless accurate or possibly misleading—and therefore not helpful toestablishing facts and evidence.

An impact involving one or more transports 104, such as an impactbetween a first transport 104A and a second transport 104B, alwaysproduces a generally loud sound or series of sounds as a direct resultof the collision. The sound level is generally measured in decibels(dB), in one example. From a point at which a sound is produced, thesound level decreases generally in proportion to distance from the soundsource. That may be true for open and unimpeded areas, but is generallynot true for complex environments such as cities with many buildings andstructures, other transports 108, and other sound sources of varyingvolume. For example, a downtown intersection in a major city at noontimemay have various construction noises, trains, traffic sounds, horns,voices, and other sounds emanating from different points andunpredictably changing from moment to moment. Because of other soundsthat may be occurring at or near the same time as the impact, thedetection range of the impact or accident may change based on where theother sounds are sourced from. That is, from a first direction, thedetection range may be correspondingly short if there are other soundsources nearby. From a second direction, the detection range may becorrespondingly long if there are not other sound sources nearby. Fromthis, it is possible to define a geolocation boundary 134 for the impactbased on decibel levels associated with the impact. Impacts may be withone or more other transports 108, as shown, or with a stationary objectsuch as a light pole, a building, or various permanent or temporarystructures. In some cases, instead of a direct impact or collision witha stationary object or another transport 104, the embodiments associatedwith FIG. 1B may also be associated with a near-impact or a dangerousdriving situation. Examples of a near-impact or a dangerous drivingsituation may include hard breaking, swerving, weaving in traffic,driving into and/or across lanes, driving off road, tailgating, notstopping at stop signs, running red lights, or any other similar type ofevent.

Within the geolocation boundary 134, there may be one or more othertransports 108, a second transport 104B involved in the impact, andvarious communication devices 138A, 138B. For example, a firstpedestrian within the geolocation boundary 134 may use a firstcommunication device 138A to capture multimedia content 142 of theimpact or accident, including any involved transports 104A/104B. Thefirst pedestrian may also transmit the captured multimedia content 142to a second communication device 138B within the geolocation boundary,as well as to other communication devices 138B associated with atransport 104 involved in the impact and other transports 108 notdirectly involved in the impact or accident. Other transports outsidethe geolocation boundary 146 would not receive the captured multimediacontent 142 from the first communication device 138A.

In some embodiments, the communication device 138 may be part of eithera transport 104 involved in the impact, another transport within thegeolocation boundary 108, or with a passenger of either the transport104 involved in the impact or another transport within the geolocationboundary 108.

The captured multimedia content 142 may include any combination of audiofile(s), video file(s), text file(s), image file(s), transporttelemetry, environmental data, traffic data, and sensor data. Thecaptured multimedia content 142 may be transmitted from thecommunication device within the geolocation boundary 138. In oneembodiment, a transport involved in the impact or accident 104A, 104Bmay transmit sensor data to the communication device 138A, which thenincludes the sensor data in the captured multimedia content 142. Sensordata may include radar data, sonar data, magnetic detector data, opticalsensor data, laser rangefinder data, or any other form of data producedby sensors associated with the transport 104, 108. The capturedmultimedia content 142 may include one or more sounds and one or morevideos. In one embodiment, when communication devices 138B receive thecaptured multimedia content, they include one or more applications thatsynchronize the one or more sounds with the one or more videos.

With transports 104 now able to communicate more globally with outsideservices and communication providers, it may be beneficial to identifyindividual transports 104 in order to distinguish from other transports108. Thus, an identifier may be permanently stored or assigned to eachtransport 104, and the identifier may accompany any rich media content112. When a transport 104 is involved with an impact or accident, aspreviously discussed, the transport 104 is associated with the impact.In one embodiment, an event may be created within an onboard computer oftransport 104, and the transport 104 identifier may be associated withthe event. In one embodiment, the onboard computer may include a memorydevice to store the event and associated identifier. In anotherembodiment, the identifier may be transmitted to the communicationdevice 142, which may include the identifier in the captured multimediacontent 142.

In one embodiment, the captured multimedia content 142 may also betransmitted to a server 116 outside the geolocation boundary 134. Thecaptured multimedia content 142 may also include one or more soundsassociated with the impact and a direction for each of the sounds. Theserver 116 may determine a number of videos based on the receivedmultimedia content 142, and associate one or more of the sounds with thevideos. The communication device 138A or the server 116 may time stampthe multimedia content with one or more of a start time and an end timefor each sound and identify a sound source for each of the sounds.

In one embodiment, one or more of the communication devices 138A, 138Btransmits the captured multimedia content 142 to a cloud server 116,which may store the multimedia content 142 to cloud storage. The server116 may be located anywhere, including in proximity to the impact oraccident or outside the proximity to the impact or accident. The server116 receives the multimedia content 142 over any type of dataconnection, but most likely through wireless connections, including butnot limited to cellular connections (i.e. 3G, 4G, 5G, LTE), internet orbroadband connections, or WIFI connections. The server 116 may includeone or more applications in a memory 706, which may determine or moresounds based on the multimedia content 142. Each of the sounds mayinclude an identification of a type of sound source (e.g. an automotivenoise of a transport 104A, 104B, an automotive noise of anothertransport 108, an impact sound associated with the transport 104A, 104B,a human voice or exclamation, a warning alarm, a skidding transport 104,108, or any other type of detected sound), a time stamp associated witha sound, a sound level or volume of the sound, a sound duration of time,and an indication of association with a different sound (e.g. apassenger voice of a passenger within the transport 104).

Determining the one or more sounds based on the multimedia content 142may in some embodiments result in a file created by the server 116 witha group of parameters (identifiers, time stamps, etc as previouslydiscussed). In some embodiments, the file may be transmitted by theserver 116 or stored in a database (not shown). The server 116 mayinclude one or more applications that perform speech recognition onsounds identified as voices. In one embodiment, the speech recognitionapplication may determine a context based on recognized speech, wherethe context may include a location, a threat, a cause of the impact oraccident, a fire or explosion, an injury or medical status, a name, anaction, a controlled substance, a hazardous material, a crime, or actualor implied violence. In one embodiment, law enforcement may be notifiedif the context is applicable to law enforcement. In one embodiment, EMSor a fire department may be notified if the context is applicable to amedical condition, a fire, a hazardous material, or an explosion. In oneembodiment, an insurance provider may be notified if the context isapplicable to a cause of the impact or accident. It should be noted thatany of the actions taken with respect to an impact or accident hereinapply equally to both near-impacts as well as dangerous drivingsituations.

FIG. 1C is a diagram illustrating capturing media from vehicles within ageofence following a dangerous driving situation 150, according toexample embodiments. A dangerous driving situation is an event involvingtransport 104 that does not necessarily end in an impact or accident.For example, driving too fast for local conditions, driving an unsafetransport (weak/no brakes or almost flat tire(s)), driving intoxicated(drugs or alcohol), or swerving outside marked road lanes are allexamples of dangerous driving situations.

Transports 104, 108 are able to detect proximity to close transports,and provide audible and/or visual warnings to a driver when reversing,changing lanes, or approaching another transport quickly withinsufficient braking, Transports 104, 108 are also able to identify manydangerous driving situations. For example, a transport 104 may detect adriver is steering erratically, speeding, changing gears dangerously, orapplying insufficient or too sudden braking. This may be due to anintoxicated driver under the influence or a driver experiencing amedical condition affecting driving.

In response to identifying the dangerous driving situation, thetransport 104 may capture first media. The first media 162 may includeany combination of an audio file, a video file, a text file, an imagefile, transport telemetry, environmental data, traffic data, or sensordata. FIG. 1C illustrates a vehicle involved in a dangerous drivingsituation 104 that captures first media 162 from four sources: a frontcamera 162A, a rear camera 162B, a left-side camera 162C, and aright-side camera 162D. In other embodiments, the first media 162 mayinclude audio and various forms of vehicular and sensor data in additionto or instead of camera video from one or more camera sources. In oneembodiment, the media 162 may also include one or more forms of audioand a direction for each of the sounds.

Next, the transport 104 involved in the dangerous driving situationestablishes a geofence 134 based on the dangerous driving situation. Inone embodiment, the geofence is within a predetermined distance 154 ofthe transport 104 involved in the dangerous driving situation. Withinthe geofence boundaries may be one or more other transports 108, variouspedestrians with communication devices, passengers with communicationdevices, or static communication devices associated with traffic controlor local buildings.

In one embodiment, another transport 108 captures second media 158, aslong as the other transport 108 is within the geofence. The second media158 includes content of the transport 104 involved in the dangerousdriving situation. The second media 158 may include any combination ofan audio file, a video file, a text file, an image file, transporttelemetry, environmental data, traffic data, or sensor data. FIG. 1Cillustrates another vehicle within the geofence 108 that captures secondmedia 158 through a front camera, of the rear quarter of a swervingtransport 104. The first 162 and second 158 media are captured by one ormore devices associated with the vehicle 104, another vehicle 108, anoccupant of the vehicle 104, or an occupant of the one or more othervehicles 108.

Once the first 162 and the second 158 media have been captured, in oneembodiment they may be transmitted to a server 116. The server 116correlates the first media 162 with the second media 158 to obtain acause for the dangerous driving situation. Each of the first 162 andsecond 158 media also may include one or more sounds associated with thedangerous driving situation and a direction for each of the sounds. Theserver 116 determines a number of videos based on the received first 162and second 158 media and synchronizes the one or more sounds with one ormore videos. The server 116 may also time stamp the first 162 and second158 media with one or more of a start time and an end time for eachsound within the first 162 and second 158 media, respectively andidentify a sound source for each of the one or more sounds. In someembodiments, the transport 104 and other transport 108 may additionallytransmit one or more of the first 162 and second 158 captured mediarelated to the dangerous driving situation to storage outside thegeofence, where the storage outside the geofence may include cloudstorage.

FIG. 1D is a diagram illustrating building a sound profile from a mediasegment corresponding to a vehicle impact 170, according to exampleembodiments. Determining the cause of an impact or accident involving atransport or transport 104 may require obtaining more data andinformation and just from the impact itself. While impact data orinformation may provide useful information as to the severity of theimpact and likely damage or injuries, the preceding and followinginformation may help to identify conditions leading up to the impact,mechanical malfunction, environmental conditions, driver distraction, amedical emergency, and passenger actions or statements following theimpact. In some cases, instead of a direct impact or collision with astationary object or another vehicle 104, the embodiments associatedwith FIG. 1D may also be associated with a near-impact or a dangerousdriving situation. Examples of a near-impact or a dangerous drivingsituation may include hard breaking, swerving, weaving in traffic,driving into and/or across lanes, driving off road, tailgating, notstopping at stop signs, running red lights, or any other similar type ofevent.

A transport 104 may have one or more computing devices 174 associatedwith the transport 104. Some computing devices 174 may be directlyassociated with the transport 174 itself, such as an onboard navigationor communication system. Other computing devices 174 may be directlyassociated with one or more passengers or the driver of the transport104, such as but not limited to a cell phone, smart phone, tablet, orsmart watch. In one embodiment, computing devices 174 capture and savemedia related to the impact or accident. In one embodiment, thetransport 104 itself captures media related to the accident, transfersthe media to a computing device 174 that stores the media, and thecomputing device 174 communicates the saved media related to the impactor accident as a media segment to a server 116. In yet anotherembodiment, the transport 104 itself captures and saves media related tothe accident, transfers the media to a computing device 174 thatcommunicates the media related to the impact or accident as a mediasegment 178 to a server 116. In yet another embodiment, the transport104 itself captures the media related to the accident, transfers themedia to an external computing device 174 (outside of and/or notassociated with the transport 104), which communicates the media segment178 to the server 116. The media segment 178 includes media before theimpact or accident, and media following the impact or accident. Themedia may be captured and/or stored during a first time period beforethe impact and/or during a second time period after the impact. Themedia may include any combination of one or more audio files, videofiles, text files, image files, transport telemetry, environmental data,traffic data, or sensor data. The environmental data may include datarelated to one or more of ambient temperature, road conditions, weather,wind speed or direction, time of day, and light sources.

The server 116 receives the media segment 178 from the computing device174. In one embodiment, one or more sounds may be extracted from themedia segment 178, and the media segment 178 may also include adirection for each of the sounds. The server 116 builds a sound profile182 from the media segment 178. In one embodiment, the sound profile 182may include data cataloging each sound within the media segment 178. Thedata may include a unique identifier, a starting time stamp, an endingtime stamp, a duration of the sound, a maximum sound level, anidentification of a sound source, a direction of the sound from thetransport 104, and a distance of the sound from the transport 104. Theunique identifier may include a number of a sequence (i.e. a nextavailable number), a description of the sound (e.g. “mechanical 1”,“siren 3”, etc.), or any other identifier that may differentiate eachsound from every other sound in the media segment 178. The media mayalso include one or more videos, and the sound profile 182 may associateand/or synchronize each sound with one or more videos.

The sound profile 182 may include analysis that may be useful to firstresponders 184, law enforcement 186, or insurance providers 188. In oneembodiment, the sound profile 182 may include identification of more oremore needed emergency services 184, such as EMS/paramedics, a firedepartment, hazardous material handling, or animal services. In oneembodiment, the server 116 provides all or a relevant portion of thesound profile to one or more emergency service providers 184. In anotherembodiment, the sound profile 182 may include identification of variouslaw enforcement functions, such as police or accident investigationresources. In one embodiment, the server 116 provides all or a relevantportion of the sound profile to one or more law enforcement services186. In another embodiment, the sound profile 182 may includeidentification of more ore more needed insurance providers 188, such asinsurers for the transport 104 involved in the impact or accident,insurers for other transports or transports also involved in theaccident or impact, or insurers of property involved in the accident orimpact. In one embodiment, the server 116 provides all or a relevantportion of the sound profile to one or more insurance providers 184. Thesound profile 182 may be associated with one or more passwords,certificates, or any other form of security in order to guard privacy orprotect confidential data or media.

Transports 104 involved in an impact or accident may include computingdevices 174 that include storage resources for emergency services 184,law enforcement 186, and insurance providers 188. Just after an impactor accident, involved transports 104 may automatically transfer anotification to any stored emergency services 184, law enforcement 186,and/or insurance providers 188. In one embodiment, the emergencyservices 184, law enforcement 186, and/or insurance providers 188 maycontact the server 116 to obtain all or part of the sound profile 182from the server 116. In another embodiment, the emergency services 184,law enforcement 186, and/or insurance providers 188 may contact thetransport 104 itself to obtain any stored media related to the impact oraccident, separately from or in addition to obtaining all or part of thesound profile 182 from the server 116. It should be noted that any ofthe actions taken with respect to an impact or accident herein applyequally to both near-impacts as well as dangerous driving situations.

FIG. 2A illustrates a transport network diagram 200, according toexample embodiments. The network comprises elements including atransport node 202 including a processor 204, as well as a transportnode 202′ including a processor 204′. The transport nodes 202, 202′communicate with one another via the processors 204, 204′, as well asother elements (not shown) including transceivers, transmitters,receivers, storage, sensors and other elements capable of providingcommunication. The communication between the transport nodes 202, 202′can occur directly, via a private and/or a public network (not shown) orvia other transport nodes and elements comprising one or more of aprocessor, memory, and software. Although depicted as single transportnodes and processors, a plurality of transport nodes and processors maybe present. One or more of the applications, features, steps, solutions,etc., described and/or depicted herein may be utilized and/or providedby the instant elements.

FIG. 2B illustrates another transport network diagram 210, according toexample embodiments. The network comprises elements including atransport node 202 including a processor 204, as well as a transportnode 202′ including a processor 204′. The transport nodes 202, 202′communicate with one another via the processors 204, 204′, as well asother elements (not shown) including transceivers, transmitters,receivers, storage, sensors and other elements capable of providingcommunication. The communication between the transport nodes 202, 202′can occur directly, via a private and/or a public network (not shown) orvia other transport nodes and elements comprising one or more of aprocessor, memory, and software. The processors 204, 204′ can furthercommunicate with one or more elements 230 including sensor 212, wireddevice 214, wireless device 216, database 218, mobile phone 220,transport node 222, computer 224, I/O device 226 and voice application228. The processors 204, 204′ can further communicate with elementscomprising one or more of a processor, memory, and software.

Although depicted as single transport nodes, processors and elements, aplurality of transport nodes, processors and elements may be present.Information or communication can occur to and/or from any of theprocessors 204, 204′ and elements 230. For example, the mobile phone 220may provide information to the processor 204 which may initiate thetransport node 202 to take an action, may further provide theinformation or additional information to the processor 204′ which mayinitiate the transport node 202′ to take an action, may further providethe information or additional information to the mobile phone 220, thetransport node 222, and/or the computer 224. One or more of theapplications, features, steps, solutions, etc., described and/ordepicted herein may be utilized and/or provided by the instant elements.

FIG. 2C illustrates another transport network diagram 240, according toexample embodiments. The network comprises elements including atransport node 202 including a processor 204 and a non-transitorycomputer readable medium 242C. The processor 204 is communicably coupledto the computer readable medium 242C and elements 230 (which weredepicted in FIG. 2B).

The processor 204 performs one or more of receiving, in block 244C, froma device 120 in proximity to an impact, media related to the impact,associating, in block 246C, a transport 104 with the impact, the impactin proximity to one or more other transports 108, determining, in block248C, one or more sounds based on the media, and associating, in block250C, the one or more sounds with one or more of the transport 104 andthe one or more other transports 108.

FIG. 2D illustrates a further transport network diagram 260, accordingto example embodiments. The network comprises elements including atransport node 202 including a processor 204 and a non-transitorycomputer readable medium 242D. The processor 204 is communicably coupledto the computer readable medium 242D and elements 230 (which weredepicted in FIG. 2B).

The processor 204 performs one or more of establishing, in block 244D,geolocation boundaries 134 based on decibels associated with an impactinvolving one or more transports 104A/104B, transmitting, by acommunication device 138A in block 246D, multimedia content 142 relatedto the impact to one or more other communication devices 138B within thegeolocation boundaries 134, and receiving, by the one or more othercommunication devices 138B in block 248D, the multimedia content 142.

FIG. 2E illustrates a yet further transport network diagram 270,according to example embodiments. The network comprises elementsincluding a transport node 202 including a processor 204 and anon-transitory computer readable medium 242E. The processor 204 iscommunicably coupled to the computer readable medium 242E and elements230 (which were depicted in FIG. 2B).

The processor 204 performs one or more of identifying, in block 244E, adangerous driving situation, capturing, in block 246E, first media 162by a transport 104 involved in the dangerous driving situation,establishing a geofence 134, in block 248E, based on a distanceassociated with the dangerous driving situation 154, and capturingsecond media 158, in block 250E, by one or more other transports 108within the geofence 134.

The processors and/or computer readable media may fully or partiallyreside in the interior or exterior of the transport nodes. The steps orfeatures stored in the computer readable media may be fully or partiallyperformed by any of the processors and/or elements in any order.Additionally, one or more steps or features may be added, omitted,combined, performed at a later time, etc.

FIG. 2F illustrates a yet further transport network diagram 280,according to example embodiments. The network comprises elementsincluding a transport node 202 including a processor 204 and anon-transitory computer readable medium 242F. The processor 204 iscommunicably coupled to the computer readable medium 242F and elements230 (which were depicted in FIG. 2B).

The processor 204 performs one or more of associating, in block 244F, atransport 104 with an impact, saving, in block 246F, media capturedbefore and after the impact as a media segment 178, transmitting, by acomputing device 174 in block 248F associated with the transport, themedia segment 178 to another computing device 116, and building, inblock 250F, a sound profile 182 from the media segment 178.

The processors and/or computer readable media may fully or partiallyreside in the interior or exterior of the transport nodes. The steps orfeatures stored in the computer readable media may be fully or partiallyperformed by any of the processors and/or elements in any order.Additionally, one or more steps or features may be added, omitted,combined, performed at a later time, etc.

FIG. 3A illustrates a flow diagram 300, according to exampleembodiments. Referring to FIG. 3A, a device in proximity to an impactreceives media related to the impact 302. In one embodiment, a transport104 includes one or more accelerometers that detect rapid, unusual, andpossibly instantaneous deceleration. The accelerometers may triggerinitiation of video, audio, sensor, and data media capture for thetransport 104. This may be coupled with either instantaneous streamingor delayed transfer of the media to other devices 120, which may beassociated with the driver or one or more passengers of the transport104, or a device 120 outside the transport 104. The media may include anidentifier for the transport, as described herein.

A transport is associated with the impact, which is in proximity withother transports 304. The media may include an identifier for atransport 104 involved in the impact or accident (there may be multipletransports 104, and therefore multiple identifiers). The identifier,present within the media, associates the transport 104 with the impact.On or more other transports 108 are within proximity to the impact oraccident, as previously described with respect to FIG. 1A. Proximity maybe defined in many ways, but generally is within direct line-of-sight ofthe impact and/or within hearing range of the impact. In one embodiment,proximity may be determined at one or more of before the impact, at thesame time as the impact, or after the impact.

Media related to the impact is then transmitted to a server 306. In someembodiments, the transport 104 or another transport 108 may directlytransmit the media to the server 116 through a wireless connectionincluding, but not limited to, BLUETOOTH, WIFI, a cellular connection,or a satellite connection.

The server determines one or more sounds, based on the media 308. In oneembodiment, the server 116 parses individual sounds from the media andcreates a data structure identifying (to the extent possible) eachdetected sound. The data structure may include a unique identifier foreach sound, an indication if the sound is associated or not associatedwith the impact, a start time stamp, an end time stamp, and duration foreach sound, a sound level or volume, a sound source, and a type of eachsound. For sounds identified as speech or a human exclamation, a voicerecognition software application in the server 116 may determine textfrom the recognized speech, and context for the text. In one embodiment,if the context suggests or requests assistance in any way, the servermay provide a notification to an appropriate service provider throughemail, a text message, a voice call, or any other communication method.

Finally, the server associates the sounds with the transport and theother transports 310. The analysis performed by the server 116 attemptsto identify each sound in the received media. As part of this analysis,the source of each sound is identified, if possible—including soundsassociated with the transport 104 and each of the other transports 108.If a specific transport 104, 108 may not be determined directly, volumeand direction information may be extracted from the sounds, which maythen indicate a specific transport 104, 108. In one embodiment, theserver 116 receives media and data 112 from multiple sources, possiblyincluding a transport 104 involved in the impact, one or more othertransports 108, and one or more other devices 120. An application ofserver 116 may cross-analyze each of the sounds between each of thereceived media and data streams 112, and based on volume cues andlocation information (GPS coordinates, for example), be able to makeintelligent estimation of sources for each sound element. From this, amap of events and actions may be determined to facilitate reliable andrapid accident investigation and impact or accident cause determination.

FIG. 3B illustrates another flow diagram 320, according to exampleembodiments. Referring to FIG. 3B, geolocation boundaries 134 areestablished based on impact-related decibels 322. Geolocation boundaries134 define an area of interest related to the impact or accident. Thearea of interest may be generally centered on the specific location ifthe impact or accident, but need not be circular in shape. It may beirregular, with a longer axis in one or more directions and a shorteraxis in one or more other directions. For example, an accident or impactmay occur at an intersection of two streets. Other media orcommunication devices 138 may be unpredictably oriented around theimpact or accident site, such as by merchants, pedestrians, or workersnearby. Each such device 138 may receive and detect audio related to theimpact or accident, and an application within each communication device138 may determine if the received audio is above a predeterminedthreshold. If the application determines the received audio is not abovea predetermined threshold, reflecting either too far away to be usefulor too low a level to analyze the audio and produce useful data, thereceived audio may be disregarded. If instead the application determinesthe received audio is above a predetermined threshold, the applicationmay save the audio, forward or stream the audio and any associated mediato the server, and/or save geolocation coordinates for the currentdevice 138. The coordinates may additionally be transferred to a server116 in order for an application in server 116 to construct a 2-Dgeolocation map of the impact or accident. In one embodiment, thecoordinates may be provided along with a unique identifier for thedevices 138A, 138B which transmit the coordinates and any accompanyingvideo, audio, data, or sensor data from devices 138A, 138B.

Multimedia content 142 related to the impact is transmitted to one ormore other devices 324. Finally, the other devices 138 receive themultimedia content 326. The device(s) 138 and each of the transports104A, 104B within the geolocation boundaries 134 may transmit multimediacontent 142 to other devices 138 within the geolocation boundaries 134.

FIG. 3C illustrates yet another flow diagram 340, according to exampleembodiments. Referring to FIG. 3C, a dangerous driving situation isidentified 342, as previously described. In one embodiment,accelerometers within the vehicle involved in the dangerous drivingsituation 104 may detect the vehicle 104 driving erratically, and maytrigger any of camera, audio, or sensor capture thereafter. In anotherembodiment, one or more cameras 162 or sensors within the vehicleinvolved in the dangerous driving situation 104 may detect erraticvideo, unpredictable and rapid steering changes, or speeds well inexcess of speed limits (for example), and in response trigger any ofcamera, audio, or sensor capture thereafter. In yet another embodiment,a microphone within the vehicle involved in the dangerous drivingsituation 104 may provide audio to a speech recognition applicationwithin the transport 104 and detect speech patterns or languagesuggesting, stating, or implying an impaired driver.

Next, after identifying the dangerous driving situation, first media iscaptured by the vehicle involved in the dangerous driving situation 344.First media may include any combination of video, audio, sensor data,and environmental data from single or multiple sources. For example, acar 104 may have multiple cameras 162 that may be used to capture videoor images to different directions relative to the vehicle 104.

A geofence is then established around the vehicle 346, based on distance154 from the dangerous driving situation. In one embodiment, thisdistance 154 may be a predetermined value that is always the same. Inanother embodiment, the distance 154 may be based on the type oflocation where the dangerous driving situation occurs—for example, 100feet for an urban situation, 200 feet for a suburban situation, and 1000feet for a rural situation. In yet another embodiment, the distance 154may be based on a number of other vehicles 108 in proximity to theevent—for example, a distance 154 to allow media capture from theclosest three sources may set the geofence distance to 85 feet if allthree vehicles 108 are within an 85 foot radius of the dangerous drivingsituation.

Finally, second media is captured by one or more other vehicles 108within the geofence 348. The second media is from the other vehicle'sperspective 108, and likely includes at least partially media providingdata on the dangerous driving situation. As with the first media, thesecond media may include any combination of video, audio, sensor data,and environmental data from single or multiple sources. For example, avehicle 108 may have a front camera 158 that may be used to capturevideo or images from a front direction relative to the vehicle 108. Thismay beneficially provide additional data that may support or refute datafrom the first media. After capturing the first and the second media,many follow-on actions may be possible. For example, one or morevehicles 104, 108 may transfer first and second media to lawenforcement, insurance provider, or other resources to take appropriateaction. The appropriate action may include providing a warning to thedriver of the vehicle involved in the dangerous driving situation 104,providing a traffic or other citation to the driver of the vehicleinvolved in the dangerous driving situation 104, raising insurance ratesfor the driver of the vehicle involved in the dangerous drivingsituation 104, notifying a next of kin for the driver of the vehicleinvolved in the dangerous driving situation 104, or notifying policedispatch of the location and circumstances of the dangerous drivingsituation.

FIG. 3D illustrates yet another flow diagram 360, according to exampleembodiments. Referring to FIG. 3D, a vehicle is associated with animpact 362. A vehicle may be associated with the impact, which may be inproximity with other vehicles. Media related to the impact may becaptured from several sources may and include an identifier for atransport 104 involved in the impact or accident (there may be multiplevehicles 104, and therefore multiple identifiers). The identifier,present within the media, associates the vehicle 104 with the impact.

Media is captured both before and after the impact, and saved 364. Thetransport 104 may include one or more computing devices 174 that maytransmit a media segment 178—including media captured both before andafter the impact—to a server 116 for further processing.

The captured media is transmitted to another computing device 366.Finally, a sound profile is built from the captured media 368. This hasbeen previously described in detail with respect to FIG. 1D.

FIG. 4 illustrates a machine learning transport network diagram 400,according to example embodiments. The network 400 includes a transportnode 402 that interfaces with a machine learning subsystem 406. Thetransport node includes one or more sensors 404.

The machine learning subsystem 406 contains a learning model 408 whichis a mathematical artifact created by a machine learning training system410 that generates predictions by finding patterns in one or moretraining data sets. In some embodiments, the machine learning subsystem406 resides in the transport node 402. In other embodiments, the machinelearning subsystem 406 resides outside of the transport node 402.

The transport node 402 sends data from the one or more sensors 404 tothe machine learning subsystem 406. The machine learning subsystem 406provides the one or more sensor 404 data to the learning model 408 whichreturns one or more predictions. The machine learning subsystem 406sends one or more instructions to the transport node 402 based on thepredictions from the learning model 408.

In a further embodiment, the transport node 402 may send the one or moresensor 404 data to the machine learning training system 410. In yetanother embodiment, the machine learning subsystem 406 may sent thesensor 404 data to the machine learning subsystem 410. One or more ofthe applications, features, steps, solutions, etc., described and/ordepicted herein may utilize the machine learning network 400 asdescribed herein.

FIG. 5A illustrates an example transport configuration 500 for managingdatabase transactions associated with a transport, according to exampleembodiments. Referring to FIG. 5A, as a particular transport/transport525 is engaged in transactions (e.g., transport service, dealertransactions, delivery/pickup, transportation services, etc.), thetransport may receive assets 510 and/or expel/transfer assets 512according to a transaction(s). A transport processor 526 resides in thetransport 525 and communication exists between the transport processor526, a database 530, a transport processor 526 and the transactionmodule 520. The transaction module 520 may record information, such asassets, parties, credits, service descriptions, date, time, location,results, notifications, unexpected events, etc. Those transactions inthe transaction module 520 may be replicated into a database 530. Thedatabase 530 can be one of a SQL database, an RDBMS, a relationaldatabase, a non-relational database, a blockchain, a distributed ledger,and may be on board the transport, may be off board the transport, maybe accessible directly and/or through a network, or be accessible to thetransport.

FIG. 5B illustrates an example transport configuration 550 for managingdatabase transactions conducted among various transports, according toexample embodiments. The transport 525 may engage with another transport508 to perform various actions such as to share, transfer, acquireservice calls, etc. when the transport has reached a status where theservices need to be shared with another transport. For example, thetransport 508 may be due for a battery charge and/or may have an issuewith a tire and may be in route to pick up a package for delivery. Atransport processor 528 resides in the transport 508 and communicationexists between the transport processor 528, a database 554, a transportprocessor 528 and the transaction module 552. The transport 508 maynotify another transport 525 which is in its network and which operateson its blockchain member service. A transport processor 526 resides inthe transport 525 and communication exists between the transportprocessor 526, a database 530, the transport processor 526 and atransaction module 520. The transport 525 may then receive theinformation via a wireless communication request to perform the packagepickup from the transport 508 and/or from a server (not shown). Thetransactions are logged in the transaction modules 552 and 520 of bothtransports. The credits are transferred from transport 508 to transport525 and the record of the transferred service is logged in the database530/554 assuming that the blockchains are different from one another,or, are logged in the same blockchain used by all members. The database554 can be one of a SQL database, an RDBMS, a relational database, anon-relational database, a blockchain, a distributed ledger, and may beon board the transport, may be off board the transport, may beaccessible directly and/or through a network.

FIG. 6A illustrates a blockchain architecture configuration 600,according to example embodiments. Referring to FIG. 6A, the blockchainarchitecture 600 may include certain blockchain elements, for example, agroup of blockchain member nodes 602-606 as part of a blockchain group610. In one example embodiment, a permissioned blockchain is notaccessible to all parties but only to those members with permissionedaccess to the blockchain data. The blockchain nodes participate in anumber of activities, such as blockchain entry addition and validationprocess (consensus). One or more of the blockchain nodes may endorseentries based on an endorsement policy and may provide an orderingservice for all blockchain nodes. A blockchain node may initiate ablockchain action (such as an authentication) and seek to write to ablockchain immutable ledger stored in the blockchain, a copy of whichmay also be stored on the underpinning physical infrastructure.

The blockchain transactions 620 are stored in memory of computers as thetransactions are received and approved by the consensus model dictatedby the members' nodes. Approved transactions 626 are stored in currentblocks of the blockchain and committed to the blockchain via a committalprocedure which includes performing a hash of the data contents of thetransactions in a current block and referencing a previous hash of aprevious block. Within the blockchain, one or more smart contracts 630may exist that define the terms of transaction agreements and actionsincluded in smart contract executable application code 632, such asregistered recipients, transport features, requirements, permissions,sensor thresholds, etc. The code may be configured to identify whetherrequesting entities are registered to receive transport services, whatservice features they are entitled/required to receive given theirprofile statuses and whether to monitor their actions in subsequentevents. For example, when a service event occurs and a user is riding inthe transport, the sensor data monitoring may be triggered, and acertain parameter, such as a transport charge level, may be identifiedas being above/below a particular threshold for a particular period oftime, then the result may be a change to a current status which requiresan alert to be sent to the managing party (i.e., transport owner,transport operator, server, etc.) so the service can be identified andstored for reference. The transport sensor data collected may be basedon types of sensor data used to collect information about transport'sstatus. The sensor data may also be the basis for the transport eventdata 634, such as a location(s) to be traveled, an average speed, a topspeed, acceleration rates, whether there were any collisions, was theexpected route taken, what is the next destination, whether safetymeasures are in place, whether the transport has enough charge/fuel,etc. All such information may be the basis of smart contract terms 630,which are then stored in a blockchain. For example, sensor thresholdsstored in the smart contract can be used as the basis for whether adetected service is necessary and when and where the service should beperformed.

FIG. 6B illustrates a shared ledger configuration, according to exampleembodiments. Referring to FIG. 6B, the blockchain logic example 640includes a blockchain application interface 642 as an API or plug-inapplication that links to the computing device and execution platformfor a particular transaction. The blockchain configuration 640 mayinclude one or more applications which are linked to applicationprogramming interfaces (APIs) to access and execute storedprogram/application code (e.g., smart contract executable code, smartcontracts, etc.) which can be created according to a customizedconfiguration sought by participants and can maintain their own state,control their own assets, and receive external information. This can bedeployed as an entry and installed, via appending to the distributedledger, on all blockchain nodes.

The smart contract application code 644 provides a basis for theblockchain transactions by establishing application code which whenexecuted causes the transaction terms and conditions to become active.The smart contract 630, when executed, causes certain approvedtransactions 626 to be generated, which are then forwarded to theblockchain platform 652. The platform includes a security/authorization658, computing devices which execute the transaction management 656 anda storage portion 654 as a memory that stores transactions and smartcontracts in the blockchain.

The blockchain platform may include various layers of blockchain data,services (e.g., cryptographic trust services, virtual executionenvironment, etc.), and underpinning physical computer infrastructurethat may be used to receive and store new entries and provide access toauditors which are seeking to access data entries. The blockchain mayexpose an interface that provides access to the virtual executionenvironment necessary to process the program code and engage thephysical infrastructure. Cryptographic trust services may be used toverify entries such as asset exchange entries and keep informationprivate.

The blockchain architecture configuration of FIGS. 6A and 6B may processand execute program/application code via one or more interfaces exposed,and services provided, by the blockchain platform. As a non-limitingexample, smart contracts may be created to execute reminders, updates,and/or other notifications subject to the changes, updates, etc. Thesmart contracts can themselves be used to identify rules associated withauthorization and access requirements and usage of the ledger. Forexample, the information may include a new entry, which may be processedby one or more processing entities (e.g., processors, virtual machines,etc.) included in the blockchain layer. The result may include adecision to reject or approve the new entry based on the criteriadefined in the smart contract and/or a consensus of the peers. Thephysical infrastructure may be utilized to retrieve any of the data orinformation described herein.

Within smart contract executable code, a smart contract may be createdvia a high-level application and programming language, and then writtento a block in the blockchain. The smart contract may include executablecode which is registered, stored, and/or replicated with a blockchain(e.g., distributed network of blockchain peers). An entry is anexecution of the smart contract code which can be performed in responseto conditions associated with the smart contract being satisfied. Theexecuting of the smart contract may trigger a trusted modification(s) toa state of a digital blockchain ledger. The modification(s) to theblockchain ledger caused by the smart contract execution may beautomatically replicated throughout the distributed network ofblockchain peers through one or more consensus protocols.

The smart contract may write data to the blockchain in the format ofkey-value pairs. Furthermore, the smart contract code can read thevalues stored in a blockchain and use them in application operations.The smart contract code can write the output of various logic operationsinto the blockchain. The code may be used to create a temporary datastructure in a virtual machine or other computing platform. Data writtento the blockchain can be public and/or can be encrypted and maintainedas private. The temporary data that is used/generated by the smartcontract is held in memory by the supplied execution environment, thendeleted once the data needed for the blockchain is identified.

A smart contract executable code may include the code interpretation ofa smart contract, with additional features. As described herein, thesmart contract executable code may be program code deployed on acomputing network, where it is executed and validated by chainvalidators together during a consensus process. The smart contractexecutable code receives a hash and retrieves from the blockchain a hashassociated with the data template created by use of a previously storedfeature extractor. If the hashes of the hash identifier and the hashcreated from the stored identifier template data match, then the smartcontract executable code sends an authorization key to the requestedservice. The smart contract executable code may write to the blockchaindata associated with the cryptographic details.

FIG. 6C illustrates a blockchain configuration for storing blockchaintransaction data, according to example embodiments. Referring to FIG.6C, the example configuration 660 provides for the transport 662, theuser device 664 and a server 666 sharing information with a distributedledger (i.e., blockchain) 668. The server may represent a serviceprovider entity inquiring with a transport service provider to shareuser profile rating information in the event that a known andestablished user profile is attempting to rent a transport with anestablished rated profile. The server 666 may be receiving andprocessing data related to a transport's service requirements. As theservice events occur, such as the transport sensor data indicates a needfor fuel/charge, a maintenance service, etc., a smart contract may beused to invoke rules, thresholds, sensor information gathering, etc.,which may be used to invoke the transport service event. The blockchaintransaction data 670 is saved for each transaction, such as the accessevent, the subsequent updates to a transport's service status, eventupdates, etc. The transactions may include the parties, the requirements(e.g., 18 years of age, service eligible candidate, valid driver'slicense, etc.), compensation levels, the distance traveled during theevent, the registered recipients permitted to access the event and hosta transport service, rights/permissions, sensor data retrieved duringthe transport event operation to log details of the next service eventand identify a transport's condition status, and thresholds used to makedeterminations about whether the service event was completed and whetherthe transport's condition status has changed.

FIG. 6D illustrates blockchain blocks 680 that can be added to adistributed ledger, according to example embodiments, and contents ofblock structures 682A to 682 n. Referring to FIG. 6D, clients (notshown) may submit entries to blockchain nodes to enact activity on theblockchain. As an example, clients may be applications that act onbehalf of a requester, such as a device, person or entity to proposeentries for the blockchain. The plurality of blockchain peers (e.g.,blockchain nodes) may maintain a state of the blockchain network and acopy of the distributed ledger. Different types of blockchainnodes/peers may be present in the blockchain network including endorsingpeers which simulate and endorse entries proposed by clients andcommitting peers which verify endorsements, validate entries, and commitentries to the distributed ledger. In this example, the blockchain nodesmay perform the role of endorser node, committer node, or both.

The instant system includes a blockchain which stores immutable,sequenced records in blocks, and a state database (current world state)maintaining a current state of the blockchain. One distributed ledgermay exist per channel and each peer maintains its own copy of thedistributed ledger for each channel of which they are a member. Theinstant blockchain is an entry log, structured as hash-linked blockswhere each block contains a sequence of N entries. Blocks may includevarious components such as those shown in FIG. 6D. The linking of theblocks may be generated by adding a hash of a prior block's headerwithin a block header of a current block. In this way, all entries onthe blockchain are sequenced and cryptographically linked togetherpreventing tampering with blockchain data without breaking the hashlinks. Furthermore, because of the links, the latest block in theblockchain represents every entry that has come before it. The instantblockchain may be stored on a peer file system (local or attachedstorage), which supports an append-only blockchain workload.

The current state of the blockchain and the distributed ledger may bestored in the state database. Here, the current state data representsthe latest values for all keys ever included in the chain entry log ofthe blockchain. Smart contract executable code invocations executeentries against the current state in the state database. To make thesesmart contract executable code interactions extremely efficient, thelatest values of all keys are stored in the state database. The statedatabase may include an indexed view into the entry log of theblockchain, it can therefore be regenerated from the chain at any time.The state database may automatically get recovered (or generated ifneeded) upon peer startup, before entries are accepted.

Endorsing nodes receive entries from clients and endorse the entry basedon simulated results. Endorsing nodes hold smart contracts whichsimulate the entry proposals. When an endorsing node endorses an entry,the endorsing nodes creates an entry endorsement which is a signedresponse from the endorsing node to the client application indicatingthe endorsement of the simulated entry. The method of endorsing an entrydepends on an endorsement policy which may be specified within smartcontract executable code. An example of an endorsement policy is “themajority of endorsing peers must endorse the entry.” Different channelsmay have different endorsement policies. Endorsed entries are forward bythe client application to an ordering service.

The ordering service accepts endorsed entries, orders them into a block,and delivers the blocks to the committing peers. For example, theordering service may initiate a new block when a threshold of entrieshas been reached, a timer times out, or another condition. In thisexample, blockchain node is a committing peer that has received a datablock 682A for storage on the blockchain. The ordering service may bemade up of a cluster of orderers. The ordering service does not processentries, smart contracts, or maintain the shared ledger. Rather, theordering service may accept the endorsed entries and specifies the orderin which those entries are committed to the distributed ledger. Thearchitecture of the blockchain network may be designed such that thespecific implementation of ‘ordering’ (e.g., Solo, Kafka, BFT, etc.)becomes a pluggable component.

Entries are written to the distributed ledger in a consistent order. Theorder of entries is established to ensure that the updates to the statedatabase are valid when they are committed to the network. Unlike acryptocurrency blockchain system (e.g., Bitcoin, etc.) where orderingoccurs through the solving of a cryptographic puzzle, or mining, in thisexample the parties of the distributed ledger may choose the orderingmechanism that best suits that network.

Referring to FIG. 6D, a block 682A (also referred to as a data block)that is stored on the blockchain and/or the distributed ledger mayinclude multiple data segments such as a block header 684A to 684 n,transaction specific data 686A to 686 n, and block metadata 688A to 688n. It should be appreciated that the various depicted blocks and theircontents, such as block 682A and its contents are merely for purposes ofan example and are not meant to limit the scope of the exampleembodiments. In some cases, both the block header 684A and the blockmetadata 688A may be smaller than the transaction specific data 686Awhich stores entry data; however, this is not a requirement. The block682A may store transactional information of N entries (e.g., 100, 500,1000, 2000, 3000, etc.) within the block data 690A to 690 n. The block682A may also include a link to a previous block (e.g., on theblockchain) within the block header 684A. In particular, the blockheader 684A may include a hash of a previous block's header. The blockheader 684A may also include a unique block number, a hash of the blockdata 690A of the current block 682A, and the like. The block number ofthe block 682A may be unique and assigned in an incremental/sequentialorder starting from zero. The first block in the blockchain may bereferred to as a genesis block which includes information about theblockchain, its members, the data stored therein, etc.

The block data 690A may store entry information of each entry that isrecorded within the block. For example, the entry data may include oneor more of a type of the entry, a version, a timestamp, a channel ID ofthe distributed ledger, an entry ID, an epoch, a payload visibility, asmart contract executable code path (deploy tx), a smart contractexecutable code name, a smart contract executable code version, input(smart contract executable code and functions), a client (creator)identify such as a public key and certificate, a signature of theclient, identities of endorsers, endorser signatures, a proposal hash,smart contract executable code events, response status, namespace, aread set (list of key and version read by the entry, etc.), a write set(list of key and value, etc.), a start key, an end key, a list of keys,a Merkel tree query summary, and the like. The entry data may be storedfor each of the N entries.

In some embodiments, the block data 690A may also store transactionspecific data 686A which adds additional information to the hash-linkedchain of blocks in the blockchain. Accordingly, the data 686A can bestored in an immutable log of blocks on the distributed ledger. Some ofthe benefits of storing such data 686A are reflected in the variousembodiments disclosed and depicted herein. The block metadata 688A maystore multiple fields of metadata (e.g., as a byte array, etc.).Metadata fields may include signature on block creation, a reference toa last configuration block, an entry filter identifying valid andinvalid entries within the block, last offset persisted of an orderingservice that ordered the block, and the like. The signature, the lastconfiguration block, and the orderer metadata may be added by theordering service. Meanwhile, a committer of the block (such as ablockchain node) may add validity/invalidity information based on anendorsement policy, verification of read/write sets, and the like. Theentry filter may include a byte array of a size equal to the number ofentries in the block data 610A and a validation code identifying whetheran entry was valid/invalid.

The other blocks 682B to 682 n in the blockchain also have headers,files, and values. However, unlike the first block 682A, each of theheaders 684A to 684 n in the other blocks includes the hash value of animmediately preceding block. The hash value of the immediately precedingblock may be just the hash of the header of the previous block or may bethe hash value of the entire previous block. By including the hash valueof a preceding block in each of the remaining blocks, a trace can beperformed from the Nth block back to the genesis block (and theassociated original file) on a block-by-block basis, as indicated byarrows 692, to establish an auditable and immutable chain-of-custody.

The above embodiments may be implemented in hardware, in a computerprogram executed by a processor, in firmware, or in a combination of theabove. A computer program may be embodied on a computer readable medium,such as a storage medium. For example, a computer program may reside inrandom access memory (“RAM”), flash memory, read-only memory (“ROM”),erasable programmable read-only memory (“EPROM”), electrically erasableprogrammable read-only memory (“EEPROM”), registers, hard disk, aremovable disk, a compact disk read-only memory (“CD-ROM”), or any otherform of storage medium known in the art.

An exemplary storage medium may be coupled to the processor such thatthe processor may read information from, and write information to, thestorage medium. In the alternative, the storage medium may be integralto the processor. The processor and the storage medium may reside in anapplication specific integrated circuit (“ASIC”). In the alternative,the processor and the storage medium may reside as discrete components.For example, FIG. 7 illustrates an example computer system architecture700, which may represent or be integrated in any of the above-describedcomponents, etc.

FIG. 7 is not intended to suggest any limitation as to the scope of useor functionality of embodiments of the application described herein.Regardless, the computing node 700 is capable of being implementedand/or performing any of the functionality set forth hereinabove.

In computing node 700 there is a computer system/server 702, which isoperational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 702 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 702 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 702 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 7, computer system/server 702 in cloud computing node700 is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 702 may include, but are notlimited to, one or more processors or processing units 704, a systemmemory 706, and a bus that couples various system components includingsystem memory 706 to processor 704.

The bus represents one or more of any of several types of busstructures, including a memory bus or memory controller, a peripheralbus, an accelerated graphics port, and a processor or local bus usingany of a variety of bus architectures. By way of example, and notlimitation, such architectures include Industry Standard Architecture(ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA)bus, Video Electronics Standards Association (VESA) local bus, andPeripheral Component Interconnects (PCI) bus.

Computer system/server 702 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 702, and it includes both volatileand non-volatile media, removable and non-removable media. System memory706, in one embodiment, implements the flow diagrams of the otherfigures. The system memory 706 can include computer system readablemedia in the form of volatile memory, such as random-access memory (RAM)708 and/or cache memory 710. Computer system/server 702 may furtherinclude other removable/non-removable, volatile/non-volatile computersystem storage media. By way of example only, memory 706 can be providedfor reading from and writing to a non-removable, non-volatile magneticmedia (not shown and typically called a “hard drive”). Although notshown, a magnetic disk drive for reading from and writing to aremovable, non-volatile magnetic disk (e.g., a “floppy disk”), and anoptical disk drive for reading from or writing to a removable,non-volatile optical disk such as a CD-ROM, DVD-ROM or other opticalmedia can be provided. In such instances, each can be connected to thebus by one or more data media interfaces. As will be further depictedand described below, memory 706 may include at least one program producthaving a set (e.g., at least one) of program modules that are configuredto carry out the functions of various embodiments of the application.

Program/utility, having a set (at least one) of program modules, may bestored in memory 706 by way of example, and not limitation, as well asan operating system, one or more application programs, other programmodules, and program data. Each of the operating system, one or moreapplication programs, other program modules, and program data or somecombination thereof, may include an implementation of a networkingenvironment. Program modules generally carry out the functions and/ormethodologies of various embodiments of the application as describedherein.

As will be appreciated by one skilled in the art, aspects of the presentapplication may be embodied as a system, method, or computer programproduct. Accordingly, aspects of the present application may take theform of an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present application may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Computer system/server 702 may also communicate with one or moreexternal devices via an I/O device 712 (such as an I/O adapter), whichmay include a keyboard, a pointing device, a display, a voicerecognition module, etc., one or more devices that enable a user tointeract with computer system/server 702, and/or any devices (e.g.,network card, modem, etc.) that enable computer system/server 702 tocommunicate with one or more other computing devices. Such communicationcan occur via I/O interfaces of the device 712. Still yet, computersystem/server 702 can communicate with one or more networks such as alocal area network (LAN), a general wide area network (WAN), and/or apublic network (e.g., the Internet) via a network adapter. As depicted,device 712 communicates with the other components of computersystem/server 702 via a bus. It should be understood that although notshown, other hardware and/or software components could be used inconjunction with computer system/server 702. Examples, include, but arenot limited to: microcode, device drivers, redundant processing units,external disk drive arrays, RAID systems, tape drives, and data archivalstorage systems, etc.

Although an exemplary embodiment of at least one of a system, method,and non-transitory computer readable medium has been illustrated in theaccompanied drawings and described in the foregoing detaileddescription, it will be understood that the application is not limitedto the embodiments disclosed, but is capable of numerous rearrangements,modifications, and substitutions as set forth and defined by thefollowing claims. For example, the capabilities of the system of thevarious figures can be performed by one or more of the modules orcomponents described herein or in a distributed architecture and mayinclude a transmitter, receiver or pair of both. For example, all orpart of the functionality performed by the individual modules, may beperformed by one or more of these modules. Further, the functionalitydescribed herein may be performed at various times and in relation tovarious events, internal or external to the modules or components. Also,the information sent between various modules can be sent between themodules via at least one of: a data network, the Internet, a voicenetwork, an Internet Protocol network, a wireless device, a wired deviceand/or via plurality of protocols. Also, the messages sent or receivedby any of the modules may be sent or received directly and/or via one ormore of the other modules.

One skilled in the art will appreciate that a “system” could be embodiedas a personal computer, a server, a console, a personal digitalassistant (PDA), a cell phone, a tablet computing device, a smartphoneor any other suitable computing device, or combination of devices.Presenting the above-described functions as being performed by a“system” is not intended to limit the scope of the present applicationin any way but is intended to provide one example of many embodiments.Indeed, methods, systems and apparatuses disclosed herein may beimplemented in localized and distributed forms consistent with computingtechnology.

It should be noted that some of the system features described in thisspecification have been presented as modules, in order to moreparticularly emphasize their implementation independence. For example, amodule may be implemented as a hardware circuit comprising custom verylarge-scale integration (VLSI) circuits or gate arrays, off-the-shelfsemiconductors such as logic chips, transistors, or other discretecomponents. A module may also be implemented in programmable hardwaredevices such as field programmable gate arrays, programmable arraylogic, programmable logic devices, graphics processing units, or thelike.

A module may also be at least partially implemented in software forexecution by various types of processors. An identified unit ofexecutable code may, for instance, comprise one or more physical orlogical blocks of computer instructions that may, for instance, beorganized as an object, procedure, or function. Nevertheless, theexecutables of an identified module need not be physically locatedtogether but may comprise disparate instructions stored in differentlocations which, when joined logically together, comprise the module andachieve the stated purpose for the module. Further, modules may bestored on a computer-readable medium, which may be, for instance, a harddisk drive, flash device, random access memory (RAM), tape, or any othersuch medium used to store data.

Indeed, a module of executable code could be a single instruction, ormany instructions, and may even be distributed over several differentcode segments, among different programs, and across several memorydevices. Similarly, operational data may be identified and illustratedherein within modules and may be embodied in any suitable form andorganized within any suitable type of data structure. The operationaldata may be collected as a single data set or may be distributed overdifferent locations including over different storage devices, and mayexist, at least partially, merely as electronic signals on a system ornetwork.

It will be readily understood that the components of the application, asgenerally described and illustrated in the figures herein, may bearranged and designed in a wide variety of different configurations.Thus, the detailed description of the embodiments is not intended tolimit the scope of the application as claimed but is merelyrepresentative of selected embodiments of the application.

One having ordinary skill in the art will readily understand that theabove may be practiced with steps in a different order, and/or withhardware elements in configurations that are different than those whichare disclosed. Therefore, although the application has been describedbased upon these preferred embodiments, it would be apparent to those ofskill in the art that certain modifications, variations, and alternativeconstructions would be apparent.

While preferred embodiments of the present application have beendescribed, it is to be understood that the embodiments described areillustrative only and the scope of the application is to be definedsolely by the appended claims when considered with a full range ofequivalents and modifications (e.g., protocols, hardware devices,software platforms etc.) thereto.

What is claimed is:
 1. A method, comprising: associating a vehicle withan impact; saving media captured before and after the impact as a mediasegment; transmitting, by a computing device associated with thevehicle, the media segment to another computing device; and building asound profile from the media segment.
 2. The method of claim 1, whereinthe media segment comprises one or more of audio, video, a text file, animage file, vehicle telemetry, environmental data, traffic data, andsensor data.
 3. The method of claim 2, wherein environmental datacomprises data related to one or more of ambient temperature, roadconditions, weather, wind speed or direction, time of day, and lightsources.
 4. The method of claim 1, wherein the media segment furthercomprises one or more of a direction for each of one or more sounds,wherein another computing device comprises a server, wherein the methodfurther comprising: determining, at the server, a number of videos basedon the received media segment; and synchronizing the one or more soundswith one or more videos.
 5. The method of claim 1, wherein the mediasegment comprises media captured during a first time period before theimpact and media captured during a second time period after the impact.6. The method of claim 1, wherein the sound profile comprises one ormore sound elements, wherein each sound element comprising: a uniqueidentifier; a starting timestamp; an ending timestamp; and an indicationof a source of the sound element.
 7. The method of claim 6, furthercomprising: transmitting the sound profile to one of an emergencyservices provider, law enforcement, or an insurance provider.
 8. Avehicle, comprising: a processor; and a memory, coupled to theprocessor, comprising instructions that when executed by the processorare configured to: detect an impact; save media captured before andafter the impact as a media segment; and transmit, by a computing deviceassociated with the vehicle, the media segment to another computingdevice; and build a sound profile from the media segment.
 9. The vehicleof claim 8, wherein the media segment comprises one or more of audio,video, a text file, an image file, vehicle telemetry, environmentaldata, traffic data, and sensor data.
 10. The vehicle of claim 9, whereinenvironmental data comprises data related to one or more of ambienttemperature, road conditions, weather, wind speed or direction, time ofday, and light sources.
 11. The vehicle of claim 8, wherein the mediasegment further comprises one or more of a direction for each of one ormore sounds, wherein another computing device comprises a server,wherein the server determines a number of videos based on the receivedmedia segment and synchronizes the one or more sounds with one or morevideos.
 12. The vehicle of claim 11, wherein the server is furtherconfigured to transmit the sound profile to one of an emergency servicesprovider, law enforcement, or an insurance provider.
 13. The vehicle ofclaim 8, wherein the media segment comprises media captured during afirst time period before the impact and media captured during a secondtime period after the impact.
 14. The vehicle of claim 8, wherein thesound profile comprises one or more sound elements, wherein each soundelement comprising: a unique identifier; a starting timestamp; an endingtimestamp; and an indication of a source of the sound element.
 15. Anon-transitory computer readable medium comprising instructions, thatwhen read by a processor, cause the processor to perform: associating avehicle with an impact; saving media captured before and after theimpact as a media segment; transmitting, by a computing deviceassociated with the vehicle, the media segment to another computingdevice; and building a sound profile from the media segment.
 16. Thenon-transitory computer readable medium of claim 15, wherein the mediasegment comprises one or more of audio, video, a text file, an imagefile, vehicle telemetry, environmental data, traffic data, and sensordata, wherein environmental data comprises data related to one or moreof ambient temperature, road conditions, weather, wind speed ordirection, time of day, and light sources.
 17. The non-transitorycomputer readable medium of claim 15, wherein the media segmentcomprises media captured during a first time period before the impactand media captured during a second time period after the impact.
 18. Thenon-transitory computer readable medium of claim 15, wherein the soundprofile comprises one or more sound elements, wherein each sound elementcomprises: a unique identifier; a starting timestamp; an endingtimestamp; and an indication of a source of the sound element.
 19. Thenon-transitory computer readable medium of claim 15, wherein the mediasegment further comprises one or more of a direction for each of one ormore sounds, wherein another computing device comprises a server,wherein the server is configured to: determine a number of videos basedon the received media segment; and synchronize the one or more soundswith one or more videos.
 20. The non-transitory computer readable mediumof claim 19, wherein the server is further configured to: build thesound profile from the media segment; and transmit the sound profile toone of an emergency services provider, law enforcement, or an insuranceprovider.